Ecosystem method of aggregation and search and related techniques

ABSTRACT

Techniques are described for effecting data aggregation in a network. Event notifications are received from a plurality of content sites on the network. Each event notification indicates occurrence of an event associated with a corresponding one of the content sites. Each event corresponds to a change to content associated with the corresponding content site. In response to each event notification, event metadata are generated. The event metadata include a time stamp for the event and change data corresponding to the change to the content. The event metadata are indexed in a plurality of databases with reference to a plurality of index metrics including the time stamp. The indexing of the event metadata for each event occurs within days, hours, or even minutes of receipt of the corresponding event notification thereby enabling retrieving of the changes to the content from the plurality of databases using any of the index metrics in near real time.

RELATED APPLICATION DATA

The present application is a continuation of and claims priority under35 U.S.C. 120 to U.S. patent application Ser. No. 11/157,491 forECOSYSTEM METHOD OF AGGREGATION AND SEARCH AND RELATED TECHNIQUES filedon Jun. 20, 2005, which claims priority under 35 U.S.C. 119(e) to U.S.Provisional Application No. 60/584,613 for ECOSYSTEM METHOD OFAGGREGATION AND SEARCH AND RELATED TECHNIQUES filed Jun. 30, 2004, theentire disclosure of each of which is incorporated herein by referencefor all purposes.

BACKGROUND OF THE INVENTION

The present invention relates to the monitoring of dynamic content innetworks, e.g., the Internet, and, more specifically, to techniqueswhich facilitate the monitoring and indexing of such content in nearreal time.

A vast array of software solutions facilitates the publishing ofuser-generated content on the Web and the Internet. Some solutions arehosted. Others operate from the user's machine or server. Some arehighly configurable, providing source code which the user may customize.Current and past examples of such solutions within the context ofso-called “Web logs” include Radio UserLand, Movable Type, Word Press,Live Journal, B2, Grey Matter, Blossom, Blogger, Blogspot, Type Pad,Xanga, Diaryland, Nifty, etc. In general, most of these tools andsolutions may be thought of as relatively simple content managementsystems which facilitate “personal publishing.” The availability ofthese tools has resulted in the proliferation of Web logs, or “blogs,”which are typically generated by individuals on the Web.

A typical blog might include a series of postings by the “blogger,” orauthor of the content in the postings, relating to one or more topics. Aposting might also include, for example, a link to an article relatingto a current event being discussed, a link to another blog upon whichthe blogger is commenting or to which the blogger is responding, or alink to an authority on the subject of the posting. Blogs may alsocontain links outside of the regular postings which point to sites ordocuments in which the blogger has an interest, or to other blogs (i.e.,blog roll). Blogs often include a calendar with links to an archive ofhistorical postings on the blog. Obviously, these are merely exemplarycharacteristics of a blog, and are useful in pointing out the fact thatblogs have a relatively structured way in which information ispresented. In addition, blogs are only one example of mechanisms bywhich content may be dynamically published in electronic networks. Thepoint is that there is a huge amount of content being dynamicallygenerated and published on the Web and the Internet which includes linksto other content and information, and which may be thought of as ongoing“conversations.”

And, as has been posited on the Internet, one can think of these ongoingand interconnected conversations as markets (e.g., see The CluetrainManifesto). This is to be contrasted with the traditional market modelwhich defines markets primarily with respect to transactions. Relyingprimarily on information relating to transactions to monitor or evaluatea market arguably misses the most relevant information relating to themarket being monitored or evaluated. Such a conventional approach can belikened to focusing on patterns of punctuation in a document rather thanthe substance of the document. And if one begins to focus on thesubstance of the conversations relating to a particular market ratherthan mere transaction data, the exercise then becomes tracking theseconversations in meaningful and timely ways.

Unfortunately, most of the tools currently available on the Web and onthe Internet are inadequate for such a task. For example, because of theway in which they operate, most search engines on the Internet are weeksor months behind in identifying and cataloguing the constantly changingcontent on the Web. That is, the typical search engine periodically“crawls” the Web to construct an enormous database which is,essentially, a copy of the Web. Given the size of the Web, these crawlsmay require on the order of weeks to complete. And there are many whoassert that such crawling technologies are only actually looking at lessthan 10% of the content available on the Web. In any case, once thedocuments are identified, a reverse index is created using a key wordvocabulary, and then the documents are then scored relative to those keywords. All of this information is then pushed to query servers whichrespond to key word searches.

Given the time required to perform all of these tasks, it becomesapparent that traditional search engines are not particularly effectivefor identifying anything on the Web which is less than a couple of weeksold. In addition, because search engines are typically agnostic withregard to the time at which documents were created or modified, they arenot particularly useful for finding content created within particulartime ranges or with reference to any time-related metric.

In view of the foregoing, there is a need to provide mechanisms by whichdynamic content on the Web and on the Internet may be indexed,monitored, and evaluated substantially in real time.

SUMMARY OF THE INVENTION

According to the present invention, techniques are provided foreffecting data aggregation in a network. Event notifications arereceived from a plurality of content sites on the network. Each eventnotification indicates occurrence of an event associated with acorresponding one of the content sites. Each event corresponds to achange to content associated with the corresponding content site. Inresponse to each event notification, event metadata are generated. Theevent metadata include a time stamp for the event and change datacorresponding to the change to the content. The event metadata areindexed in a plurality of databases with reference to a plurality ofindex metrics including the time stamp. The indexing of the eventmetadata for each event occurs within seven days of receipt of thecorresponding event notification thereby enabling retrieving of thechanges to the content from the plurality of databases using any of theindex metrics in near real time. According to various embodiments, theindexing of the event metadata occurs within a day, hours, or evenminutes of receipt of the event notification.

A further understanding of the nature and advantages of the presentinvention may be realized by reference to the remaining portions of thespecification and the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified network diagram of an exemplary system for dataaggregation and search according to a specific embodiment of theinvention.

FIG. 2 is a flowchart illustrating a technique for aggregating data in anetwork environment according to a specific embodiment of the invention.

FIG. 3 is a simplified block diagram of a database architecture for usewith various embodiments of the invention.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS

Reference will now be made in detail to specific embodiments of theinvention including the best modes contemplated by the inventors forcarrying out the invention. Examples of these specific embodiments areillustrated in the accompanying drawings. While the invention isdescribed in conjunction with these specific embodiments, it will beunderstood that it is not intended to limit the invention to thedescribed embodiments. On the contrary, it is intended to coveralternatives, modifications, and equivalents as may be included withinthe spirit and scope of the invention as defined by the appended claims.In the following description, specific details are set forth in order toprovide a thorough understanding of the present invention. The presentinvention may be practiced without some or all of these specificdetails. In addition, well known features may not have been described indetail to avoid unnecessarily obscuring the invention.

According to the invention, an event-driven method of data aggregationand indexing is provided. According to various embodiments of theinvention, the present invention allows dynamic information to betracked, indexed, and searched in a timely manner, i.e., in near realtime. According to some embodiments, such techniques take advantage ofthe semi-structured nature of content published on the Web to trackrelevant information about the content within minutes rather than weeks.

Specific implementations of the present invention employ a“service-oriented architecture” (SOA) in which the functional blocksreferred to are assumed to be different types of services (i.e.,software objects with well defined interfaces) interacting with otherservices in the ecosystem. A service-oriented architecture (SOA) is anapplication architecture in which all functions, or services, aredefined using a description language and have invokable interfaces thatare called to perform processes. Each interaction is independent ofevery other interaction and the interconnect protocols of thecommunicating devices (i.e., the infrastructure components thatdetermine the communication system) are independent of the interfaces.Because interfaces are platform-independent, a client from any deviceusing any operating system in any language can use the service.

It will be understood, however, that the functions and processesdescribed herein may be implemented in a variety of other ways. It willalso be understood that each of the various functional blocks describedmay correspond to one or more computing platforms in a network. That is,the services and processes described herein may reside on individualmachines or be distributed across or among multiple machines in anetwork or even across networks. It should therefore be understood thatthe present invention may be implemented using any of a wide variety ofhardware, network configurations, operating systems, computingplatforms, programming languages, service oriented architectures (SOAs),communication protocols, etc., without departing from the scope of theinvention.

In some of the examples below, the content publishing and managementtools discussed are often referred to as tools for the creation andmanagement of blogs. Therefore, specific embodiments of the inventionare described for tracking blogs. However, it should be understood thatthe techniques of the present invention may relate to any tools by whichcontent may be generated and published in electronic networks, andshould therefore not be limited by references to blogs. Examples ofother such tools include, but are not limited to, wiki web page editingtools, social network profile editing tools, or any other generalpurpose or specialized content management system (CMS) or personalpublishing tools. More generally, any state change in information on anetwork which can be characterized and flagged as an event as describedherein may trigger the data aggregation and indexing techniques of thepresent invention.

Referring now to FIG. 1, an ecosystem 100 designed according to theinvention will be described. A variety of content sites 102 exist on theWeb on which content is generated and published using a variety ofcontent publishing tools and mechanisms, e.g., the blogging toolsdiscussed above. Such publishing mechanisms may reside on the sameservers or platforms on which the content resides or may be hostedservices.

A tracking site 104 is provided which receives events notifications,e.g., pings, via a wide area network 105, e.g., the Internet, each timecontent is posted or modified at any of sites 102. So, for example, ifthe content is a blog which is modified using Type Pad, when the contentcreator publishes the changes, code associated with the publishing toolmakes a connection with tracking site 104 and sends, for example, an XMLremote procedure call (XML-RPC) which identifies the name and URL of theblog. Similarly, if a news site post a new article, an eventnotification (e.g., an XML-RPC) would be generated. Tracking site 104then sends a “crawler” to that URL to parse the information found therefor the purpose of indexing the information and/or updating informationrelating to the blog in database(s) 106. According to embodimentsrelating specifically to blogs, the parsing of the information in a blogis facilitated by the fact that most blogs are similarly configured orhave a semi-structured format which either follows a general archetypeor a template provided by the well known blogging tools. According tosome embodiments, the spidering and parsing of a blog may also befacilitated by the use of, among other things, explicit and implicitalternate representations of the blog (e.g., feeds), external metadata(e.g., robots, sitemaps, and contact information files), and blogarchives.

According to some implementations, tracking site 104 may periodicallyreceive aggregated change information. For example, tracking site 104may acquire change information from other “ping” services. That is,other services, e.g., Blogger, exist which accumulate informationregarding the changes on sites which ping them directly. These changesare aggregated and made available on the site, e.g., as a changes.xmlfile. Such a file will typically have similar information as the pingsdescribed above, but may also include the time at which the identifiedcontent was modified, how often the content is updated, its URLs, andsimilar metadata. Tracking site 104 retrieves this informationperiodically, e.g., every 5 or 10 minutes, and, if it hasn't previouslyretrieved the file, sends a crawler to the indicated site, and indexesand scores the relevant information found there as described herein.

In addition, tracking site 104 (or closely associated devices orservices) may itself accumulate similar change files for periodicincorporation into the database rather than each time a ping isreceived. In any case, it should be understood that embodiments of theinvention are contemplated in which change information is acquired usingany combination of a variety of techniques.

As will be understood, event notification mechanisms, e.g., pings, maybe implemented in a wide variety of ways and may be generallycharacterized as mechanisms for notifying the system of state changes indynamic content. Such mechanisms might correspond to code integrated orassociated with a publishing tool (e.g., blog tool), a backgroundapplication on PC or web server, etc.

According to various specific embodiments, the mechanisms which generatethe pings to tracking site 104 are integrated in some way with thepublishing tool(s) being used by the authors of the content beingpublished. When an author elects to publish or post content (e.g., byselecting a “Post and Publish” object on his screen), code associatedwith the publishing tool establishes an HTTP connection with site 104 ata specific URL, and an HTTP “get” or “post” is transmitted in the formof an XML remote procedure call (RPC). This code may be provided bytracking site 104, and may simply be associated with or comprise anintegral part of the publishing tool.

According to a specific embodiment of the invention, three differentping types are employed, referred to herein as a standard blog ping, anextended blog ping, and a non-blog ping. A standard ping has twoarguments, the name of the post site or Web log and the URL. An extendedping also identifies any associated RSS feed. Standard pings aregenerally sufficient for most blog sites given relative uniformity andsemi-structured nature of the information on blog sites. The non-blogping is intended for more traditional publishers and includes the mainsite URL as well as the new URL of the recently published document. Thisping may identify any number of categories as self-selected by thepublisher, as well as arbitrary metadata such as, for example, theauthor. This information is useful in that the crawler that is sent tosuch a site will be crawling an arbitrary HTML document as opposed tothe semi-structured information in a blog. Obviously, other types ofpings and event notification mechanisms may be employed withoutdeparting from the scope of the invention.

Referring now also to the flowchart of FIG. 2, one or more notificationreceptors 108, e.g., ping servers, act as event multiplexers taking allof the event notifications (202) coming in from a variety of differentplaces and relating to a variety of different types of content and statechanges. Each notification receptor 108 understands two very importantthings about these events, i.e., the time and origin. That is,notification receptor 108 time stamps every single event when it comesin and associates the time stamp with the URL from which the eventoriginated (204). Notification receptor 108 then pushes the event onto abus 110 on which there are a number of event listeners 112 (206).

Event listeners 112 look for different types of events, e.g., pressreleases, blog postings, job listings, arbitrary webpage updates,reviews, calendars, relationships, location information, etc. Some eventlisteners may include or be associated with spiders 114 which, inresponse to recognizing a particular type of event will crawl theassociated URL to identify the state change which precipitated thenotification. Another type of event listener might be a simple counterwhich counts the number of events received of all or particular types.

An event listener might include or be associated with a re-broadcastfunctionality which re-broadcasts each of the events it is designed torecognize to some number of peers, each of which may be designed to dothe same. This, in effect, creates a federation of event listeners whichmay effect, for example, a load balancing scheme for a particular typeof event.

Another type of event listener referred to herein as a “buzz” listenermay be configured to listen for and track currently popular keywords(e.g., as determined from the content of blog postings) as an indicationof topics about which people are currently talking. Yet another type ofevent listener looks at any text associated with an event and, usingmetrics like character type and frequency, identifies the language. Withreference to the foregoing, it should be understood that event listenersmay be configured to look for and track virtually any metric ofinterest.

Once an event is recognized (208) and the event data have been acquired(210) through some mechanism, e.g., a spider, the output of the eventlisteners is a set of metadata for each event (212) including, but notlimited to, the URL (i.e., the permalink), the time stamp, the type ofevent, an event ID, content (where appropriate), and any otherstructured data or metadata associated with the event, e.g., tags,geographical information, people, events, etc. For example, the URLmight indicate that the event occurred at the New York Times web site,the time stamp the time of the event, the type of event might indicate ablog post, the event ID a post ID, and the content would include thecontent of the blog post including any links. These metadata may bederived from the information available from the URL itself, or may begenerated using some form of artificial intelligence such as, forexample, the language determination algorithm mentioned above. Inaddition to spidering, event metadata may be generated by a variety ofmeans including, for example, inferring known metadata locations, e.g.,for feeds or profile pages.

The “crawlers” employed by specific embodiments of the present inventionmay not necessarily be crawlers in the conventional sense in thattraditional crawlers are relatively autonomous and are not typicallydirected to a specific URL. By contrast, the crawlers employed by thepresent invention are directed to specific URLs or sets of URLs aslisted, for example, in the sitemap or changes.xml file(s). Thesecrawlers may employ parsers which are operable to break down theinformation being crawled and put the relevant portions, e.g., theposts, into the data model employed by the ecosystem database(s) (e.g.,database(s) 106).

According to some embodiments, site 104 maintains information, e.g.,hashes of previous posts, to ensure that only new information is indexedand scored. This, in turn, enables a very large version control systemin which different parts of an HTML document can be “aged” differently.That is, the creation date of every separable part of an HTML document,including every link, can be tracked.

According to a specific embodiment, content may be classified based onlinks to an established topic directory or ontology, e.g., by looking ateach piece of content and identifying outbound links and unusualphrases. An outbound link is then checked against an ontology (e.g.,DMOZ (see http://dmoz.org/) or any other suitable ontology) and based onthe link pattern, the content is automatically tagged as inside of thatparticular category. Then, a relevance weight may be assigned to thedocument with reference to the author's relative authority inside ofthat category (see below) as well as inbound links to that documentinside of that category. This weight may further incorporateself-categorization, (e.g. “tags”) of blogs and posts.

A number of databases 106 are maintained in which the event metadata arestored. According to a specific implementation, each event listenerand/or associated spider is operable to check the metadata for an eventagainst the database to determine whether the event metadata havealready been stored. This avoids duplicate storage of events for whichmultiple notifications have been generated. A variety of heuristics maybe employed to determine whether a new event has already been receivedand stored in the database. For example, as mentioned above, a hash ofthe metadata may be quickly compared to hashes of metadata for otherevents received for a particular URL. However, this may not besufficient in that it may not be desirable to store all content changes.

An example of a blog post may be instructive. If the intent is to storeonly events corresponding to new posts in a blog, it is important to beable to determine whether a received event corresponds to a new post orto some extraneous information embedded in a web page, e.g., recentsporting event scores. Blog publishing tools commonly create a metadatafeed (e.g., an RSS feed or Atom feed) alongside new html. A heuristiccan refer to these feeds (e.g., using link tag alternates as a sitemap)to determine whether an event corresponds to a new post. This may bedone, for example, with reference to the permalink(s) identified in thisfeed. Permalinks are the permanent links associated with content wherethat content may be found despite no longer being included at aparticular URL, e.g., a new site's home page.

Once event metadata have been generated/retrieved (212) and it has beendetermined that the event has not already been stored in the database(214), the event is once again put on bus 110 (216). A variety of datareceptors 116 (1-N) are deployed on the bus which are configured tofilter and detect particular types of events (218), e.g., blog posts,and to facilitate storage of the metadata for each recognized event inone or more of the databases (220).

According to a specific implementation, each data receptor is configuredto facilitate storage of events into a particular database. A first setof receptors 116-1 are configured to facilitate storage of events inwhat will be referred to herein as the Cosmos database (cosmos.db) 106-1which includes metadata for all events recorded by the system “since thebeginning of time.” That is, cosmos.db is the system's data warehousewhich represents the “truth” of the data universe associated withecosystem 100. All other database in the ecosystem may be derived orrepopulated from this data warehouse.

Another set of receptors 116-2 facilitates storage of events in adatabase which is ordered by time, i.e., the OBT.db 106-2. According toa specific embodiment, the information in this database is sequentiallystored in fixed amounts on individual machines. That is, once the fixedamount (which roughly corresponds to a period of time, e.g., a day, or afixed amount of storage, e.g., 4 GB RAM-based index) is stored in onemachine, the data receptor(s) feeding OBT.db move on to the nextmachine. This allows efficient retrieval of information by date andtime. For example, a user might want to know what people (or aparticular person) were talking about on a particular date, or what thebig events in the world were for a given time period.

Another set of data receptors 116-3 facilitates storage of event data ina database which is ordered by authority, i.e., the OBA.db 106-3.According to a specific embodiment, the information in this database isindexed by individuals and is ordered according to the authority orinfluence of each which may be determine, for example, by the number ofpeople linking to each individual, e.g., linking to the individual'sblog. As the number of links to individuals changes, the ordering withinthe OBA.db shifts accordingly. Such an approach allows OBA.db to besegmented across machines and database segments to effect the mostefficient retrieval of the information. For example, the informationcorresponding to authoritative individuals may be stored in a smalldatabase segment with high speed access while the information forindividuals to whom very few others link may be stored in a larger, muchslower segment.

Authority may also be determined and indexed with respect to aparticular category or subject about which an individual writes. Forexample, if an individual is identified as writing primarily about theU.S. electoral system, his authority can be determined not only withrespect to how many others link to him, but by how many othersidentifying themselves as political commentators link to him. Theauthority levels of the linking individuals may also be used to refinethe authority determination. According to some embodiments, the categoryor subject to which a particular individual's authority level relates isnot necessarily limited to or determined by the category or subjectexplicitly identified by the individual. That is, for example, ifsomeone identifies himself as a political blogger, but writes mainlyabout sports, he will be likely classified in sports. This may bedetermined with reference to the content of his posts, e.g., keywordsand/or links (e.g., a link to ESPN.com).

Yet another set of data receptors 116-4 facilitate storage of event datain a database which is ordered by keyword, i.e., the OBK.db 106-4. Thesedata receptors take the keywords in the event metadata for anincremental keyword index which is periodically (e.g., once a minute)constructed. According to a specific embodiment, these data receptorsare based on Lucene (an open source Java tool kit for text indexing andsearching) and have been tuned to enable high speed, near real-timeindexing of the keywords. Most conventional keyword indexers can takedays or weeks to create an index. That is, conventional keyword indexerscreate a data set, index the entire data set, and score the entire dataset. By contrast, the keyword indexers employed by the present inventionbuild the keyword index incrementally.

According to a specific embodiment, advantage is taken of the fact thatkeyword search may be made highly parallel. Very thin “slices” of newindex information are “layered” on top of the existing index andincorporated into the main index over time. So, for example, everyminute, the keyword data receptors add the information indexed in thepreceding minute on top of the existing index. When some number of theseone minute slices are accumulated, e.g., five, those slices areconsolidated into a single five minute slice. This repeats until somenumber (e.g., four) of five minute slices are accumulated which are thenconsolidated into a single twenty minute slice. This consolidation intothicker and thicker slices continues until a slice is consolidated whichis the size of the original underlying index, at which point,consolidation with the underlying index is effected. This approachallows structured queries for information literally within minutes oreven seconds of the information being posted on the Web or Internet. Itshould be noted that the reference to keyword indexing in this paragraphis intended to be for exemplary purposes only and should not beconstrued as limiting the incremental indexing technique described. Tothe contrary, it should be understood that this technique may be used toincorporate new index information into any type of index.

Each of the main ecosystem databases (i.e., cosmos.db, OBT.db, OBA.db,and OBK.db) includes substantially overlapping sets of information.However, each differs from the others by how the information is indexedfor response time.

When a new database is created which is to be ordered by some arbitraryindex, e.g., mp3 title, new data receptors are configured to facilitateindexing of events in the new database which, as mentioned above mayinitially be constructed from the information in cosmos.db, i.e.,information about mp3s going back “to the beginning of time.” As will beunderstood, depending upon what is being indexed some databases will notinclude the entire universe of information represented in cosmos.db.

As database receptors generate new slices for particular databases,these slices are copied to a master database for each database (e.g.,OBT.db, OBA.db, etc.) in the ecosystem. As will be discussed in greaterdetail below, there are also a number of slave database copiesassociated with each master database which are similarly updated andfrom which responses to search queries are serviced. That is, one ormore query services 118 access the slaves for each database and haveassociated query interfaces 120 which look for and present queriesappropriate to the particular database. According to specificembodiments, each slave maintains its entire copy of the database insystem RAM so that the database in long term memory is, at least duringrun time, write only. This allows queries to be serviced much morequickly than if database reads had to access long term memory. Ofcourse, it will be understood that this optimization is not necessary toimplement the invention. For example, according to other embodiments,different segments of the master database may reside in differentslaves. In one example, each slave in a cluster might store one week'sworth of postings and articles from blogs and news sites. It will beunderstood that the manner in which data are stored or segmented acrossthe slaves of a cluster may vary without departing from the invention.

Once the event metadata are indexed in the database, they are accessibleto query services 118 which service queries by users 122. In contrastwith the approach taken by the typical search engine, this processtypically takes less than a minute. That is, within a minute of changesbeing posted on the Web, the changes are available via query services118. Thus, embodiments of the present invention make it possible totrack conversations on any subject substantially in real time.

According to some embodiments, caching subsystems 124 (which may be partof or associated with the query services) are provided between the queryservices and the database(s). The caching subsystems are stored insmaller, faster memory than the databases and allow the system to handlespikes in requests for particular information. Information may be storedin the caching subsystems according to any of a variety of well knowntechniques, but due to the real-time nature of the ecosystem, it isdesirable to limit the time that any information is allowed to reside inthe cache to a relatively short period of time, e.g., on the order ofminutes. According to a specific implementation, the caching subsystemis based on the well known open source software Memcached. Informationis inserted into the cache with an expiration time at which time, theinformation is deleted or marked as “dirty.” If the cache fills up, itoperates according to any of a variety of well known techniques, e.g., a“least recently used” (LRU) algorithm, to determine which information isto be deleted.

The ecosystem of the present invention represents a fundamental paradigmshift in the way in which data are aggregated and made searchable.Instead of the conventional paradigm of simply inserting data in oneside of a database and then pulling it from the other, the universe ofdata on the Internet and the Web may be conceptualized and monitored as“streams” of information. Very simple, very fast applications (e.g.,event listeners and data receptors) are constructed which do nothing butlook for and capture specific streams of information which are thenindexed, stored, and made searchable in near real time. And becausethese applications are all operating in parallel, the information forany given “stream” does not need to be first pulled out of some largedata warehouse before it can be made available.

According to various embodiments, the event listeners and data receptorsdescribed above may be constructed from a variety of open source andproprietary software including, for example, Linux, Apache, MySQL,Python, Perl, PHP, Java, Lucene. According to a specific embodiment, themessage bus is based on open source software known as Spread. Spread isa toolkit that provides a high performance messaging service that isresilient to faults across external or internal networks. Spreadfunctions as a unified message bus for distributed applications, andprovides highly tuned application-level multicast and groupcommunication support.

According to various specific embodiments, access to the informationaccumulated by tracking site 104 may be provided in a variety of ways. Awide variety of mechanisms may be employed to enable users to get atinformation of interest indexed in the ecosystem. For example,conventional looking search interfaces may be employed which includetext boxes in which users may enter keywords, phrases, URLs, etc. Moreadvanced search tools may also be provided which, for example, enablethe construction of Boolean expressions.

Regardless of the search interface employed, query services 118corresponding to each of the databases in the ecosystem (e.g.,cosmos.db, OBT.db, OBA.db, OBK.db, etc.) look at incoming search queries(via query interfaces 120) to determine type, e.g., a keyword vs. URLsearch, with reference to the syntax or semantics of the query, e.g.,does the query text include spaces, dots (e.g., “dot” com), etc.According to embodiments employing a service oriented architecture(SOA), these query services are deployed in the architecture tostatelessly handle queries substantially in real time.

When a query service recognizes a search query which corresponds to itsdatabase, it presents the query to one or more of the slaves for thatdatabase according to any suitable load balancing scheme and/oraccording to how the data are organized across the slaves. For example,using the example mentioned above in which each slave stores aparticular week's worth of postings or articles, a query for the 20 mostrecent postings on a particular subject might result in a query serviceassociated with OBT.db connecting with some number slaves associatedwith that database and corresponding to the most recent weeks.Similarly, a query for the 20 most authoritative blog posts referring toa particular New York Times article would result in a query serviceassociated with OBA.db connecting with some number of slaves associatedwith that database. If the first slaves to which the query serviceconnects can fully satisfy the query, no further slaves need to beconsulted. On the other hand, the query service might need to connectwith additional slaves if the requested number of results are notreturned from the first set of slaves.

Keyword searching may be used to identify conversations relating tospecific subjects or issues. “Cosmos” searching may enableidentification of linking relationships. Using this capability, forexample, a blogger could find out who is linking to his blog. Thiscapability can be particularly powerful when one considers the aggregatenature of blogs.

That is, the collective community of bloggers is acting, essentially, asa very large collaborative filter on the world of information on theWeb. The links they create are their votes on the relevance and/orimportance of particular information. And the semi-structured nature ofblogs enables a systematic approach to capturing and indexing relevantinformation. Providing systematic and timely access to relevant portionsof the information which results from this collaborative process allowsspecific users to identify existing economies relating to the things inwhich they have an interest.

By being able to track links to particular content, embodiments of theinvention enable access to two important kinds of statisticalinformation. First, it is possible to identify the subjects about whicha large number of people are having conversations. And the timelinesswith which this information is acquired and indexed ensures that theseconversations are reflective of the current state of the “market” or“economy” relating to those subjects. Second, it is possible to identifythe content authors who may be considered authorities or influencers forparticular subjects, i.e., by tracking the number of people linking tothe content generated by those authors.

In addition, embodiments of the present invention are operable to trackwhat subject matter specific individuals are either linking to orwriting about over time. That is, a profile of the person who creates aset of documents may be generated over time and used as a representationof that person's preferences and interests. By indexing individualsaccording to these categories, it becomes possible to identify specificindividuals as authorities or as influential with respect to specificsubject matter. That is, for example, if a particular individual posts asignificant amount of content relating to digital music players, thatindividual's level of authority (or influence) with regard to digitalmusic players can be determined by identifying how many otherindividuals who are also interested in or authoritative with respect todigital music players (as tracked through their posts and links) link tothe first individual. This enables the creation of a rich, detailedbreakdown of the relative authority of each author across all topics inthe ontology, based on the number of inbound links by other authors whocreate documents in that category.

And because the ecosystem “understands” when a piece of content, e.g.,post, link, phrase, etc., was created, this information may be used asan additional input to any analysis of the data. For example, using timeto enhance the understanding of influence of a document (or of an authorwho created the document) by looking at the patterns of inbound linkingto a set of documents, you can quickly determine if someone is early tolink to a document or late to link to a document. If a personconsistently links early to interesting documents, then that person ismost likely an expert in that field, or at least can speakauthoritatively in that field.

Identifying and tracking authorities for particular subjects enablessome capabilities not possible using conventional search enginemethodologies. For example, the relevance of a new document indexed by asearch engine is completely indeterminate because, by virtue of itsbeing new, no one has yet linked to it. By contrast, because embodimentsof the present invention track the influence of a particular author in agiven subject matter area, new posts from that author can be immediatelyscored based on the author's influence. That is, using the newfoundunderstanding of time and personality in document creation, we are ableto immediately score new documents even though they are not yet linkedwidely because we know (a) what is in the new/updated document and cantherefore use classification methods to determine its topic, and (b) therelative authority of the author in the topic area described. So, incontrast with traditional search engines, the present invention canprovide virtually immediate access to the most relevant content.

In addition, the techniques of the present invention may be used totrack the sub-topics within a particular subject matter area which arecurrently being discussed by the most influential authors in that area.For example, one might query the database regarding the topics currentlybeing discussed by the 10 most influential authors in a particularsubject matter area.

As mentioned above, tracking the posting of and linking to content byindividuals (particularly authoritative individuals) over timeessentially results in a collaborative filtering effect for any givensubject or topic. Therefore, instead of relying on the editorial choicesof the available news sources on the Web to inform one as to what iscurrently important, the collaborative filter enabled by the presentinvention may be used to provide vastly different perspectives on whatis important and why.

For example, the present invention may be employed to track to whatarticles at the major news sites bloggers are currently linking. Thatis, the way in which the data acquired by the tracking site areorganized allows not only searching by subject matter or author (i.e.,“deep” searches), but by time (i.e., “wide” search). So, for example,all of the blog posts of the past 3 hours (or even within a rolling timewindow) may be evaluated to identify the most-linked-to news stories(and/or books, movies, etc.) about which some or all bloggers areposting content. This information may then be exposed on a Web page asthe topics currently considered important by the blogging community. Andgiven the global scope of the Web, the evolution of the topics ofimportance can be observed with the rotation of the globe through theuse of a rolling window of time. The rolling time window could beextended arbitrarily, e.g., to 12 hours (or 24/48/72 hours, 7 days,etc.), to better identify and rank the specific news articles (and/orbooks, movies, etc.) to which some or all bloggers are linking.

According to various embodiments, a variety of services may be providedwhich are based on the data collected according to the invention. Forexample, a major news service could be provided with what a community ofindividuals linking to its site are currently saying about the newsservice and specific articles posted by the news service. In addition,information relating to other aspects of this “community of interest”may be provided to the news service. That is, given that the newsservice obviously has the attention of the individuals in thiscommunity, it could be relevant to identify what else this communitymight be talking about. In some sense, this could be like having adedicated and nearly instantaneous focus group on the news service'seditorial decisions. This information could be syndicated to the newsservice and used in any of a wide variety of ways including, forexample, to generate story ideas (i.e., this is what our readers areinterested in), hiring leads (i.e., many of our readers link to somecolumnist in Topeka, Kans.), or even be directly exposed on the Web insome way (i.e., here is what our community of readers is saying). Itwill be understood that a variety of sophisticated data analysistechniques may be employed to provide information of interest from sucha data set.

As will be understood, such a community of interest can be identifiedfor any Web site. In fact, different communities of interest fordifferent Web sites, publications, subject matter areas, etc., can beidentified and exposed (e.g., on a Web site) to enable users to consumewhat is being talked about regarding any specific publication or topic,e.g., sports news, technology news, right wing political news, left wingpolitical news, etc.

So, through an understanding of time and individuals, embodiments of thepresent invention are able to discern categorization and authority, aswell as authority within specific categories. And because data analysisof this information is able to “pivot” on a variety of metrics, both“deep” and “wide” searches may be effected to yield a variety ofinteresting information which is beyond the capabilities of traditionalsearch technology.

Moreover, the ecosystem method of aggregation and search describedherein may be applied in a wide variety of contexts. For example, anecosystem may be implemented to track the way individuals sell things onthe Internet. Thus, for example, if an individual posts an auction on anauction site, this event could trigger the generation of a ping or othernotification mechanism which precipitates the transmission of a crawlerwhich parses, indexes, and scores the newly posted auction in a mannersimilar to that described above. Another example is the release of a newbook on a large retailer's site. In fact, any type of content publishedon the Web or Internet can be indexed and scored in this manner. Anotherexample is the publication of press releases on the PR Newswire.

As will be understood, the timely capture of such publications enables avariety of additional services. For example, because a person havingsignificant influence in the market for digital music players can bereadily identified, such a person may wish to be an advertisingaffiliate and post notifications on his site of specific types of events(e.g., the publication of an auction for a digital music player) whichare tailored specifically to his visitors. Such an individual might alsowant a “live” feed from publishers and sites which notifies him ofpublication events relating to his field of interest or expertise.

Similarly, instead of pushing company news to the PR Newswire, a companycan post it to its own site and ping or send changes information to atracking site which then acquires, indexes and scores the informationfor use in any of a variety of ways. For example, individuals cansubscribe to filters which will cause them to be notified of such postsrelating to specific topics.

In another example, when an employment related site posts a new resume,a tracking site can be notified, and the resume can be indexed andscored such that employers who have subscribed to appropriate filterscan then be notified if the posted resume fits their criteria. To makethe parsing of the resume information easier, the resume can have astandardized format and may, for example, comprise a templated XMLdocument. This approach also allows the publisher of the content, e.g.,the job applicant, to retain some amount of control over his data. Thatis, because the content, e.g., the resume, is typically published on thecontent creators' site, the content creator can continue to exerciseeditorial control, including taking the information down.

As should be apparent, the event-driven ecosystem of the presentinvention looks at the World Wide Web in a different way thanconventional search technologies. That is, the approach to dataaggregation and search described herein understands timeliness (e.g.,two minutes old instead of two weeks old), time (i.e., when something iscreated), and people and conversations (i.e., instead of documents).Thus, the ecosystem of the present invention enables a variety ofapplications which have not been possible before. For example, theecosystem of the present invention enables sophisticated social networkanalysis of dynamic content on the Web. The ecosystem can track not onlywhat is being said, but who is saying it, and when. Using such anapproach, it is possible to identify the first person who was first toarticulate something on the Web. It is possible to analyze how ideaspropagate on the Web; to determine who is influential, authoritative, orpopular (e.g., by how many people link to this person). It is alsopossible to determine when people linked to a particular person. Thiskind of information may be used to enable many kinds of further analysisnever before practicable.

For example, the blogosphere often “lights up” with respect to aparticular topic (e.g., the President's National Guard scandal, rolloutof the iPod mini at MacWorld Expo, etc.) in response to a recent articleor news report. That is, many bloggers start “conversing” about thetopic in response to the breaking of the news in the mainstream media.Not only does the present invention enable tracking of theseconversations, it also enables the identification of individuals whowere talking about the topic before release of the news. As will beunderstood, the ability to identify such “conversation starters” orinfluencers relating to particular topics is extremely valuable from anumber of perspectives.

According to other embodiments, the ecosystem of the present inventioncan enable meaningful tracking of return on investment (ROI) for publicrelations. Conventional techniques for doing this are ineffective inthat they don't typically provide much meaningful information. Forexample, one approach involves simply putting together a scrap bookincluding any article in which a company was mentioned over some periodof time, e.g., typically 30-90 days. Other than frequency, thisinformation provides almost no other qualitative or quantitativeinformation which may be readily used by the company to determinewhether their PR dollars have been well spent. In fact, to date, thereare virtually no consistent or reliable techniques for determining theeffectiveness of PR dollars.

By contrast, the ecosystem of the present invention enables real-timetracking of conversations which are specifically about a particularmarketing campaign including, for example, who is talking about thecampaign and what they are actually saying about it. Thus, not only cana company identify the best way to create a “buzz” about their products,but it can also track the buzz, and, through timely access to dynamiccontent, tie it directly to PR dollars spent.

PR crises can also be tracked and managed using the ecosystem of thepresent invention. For example, if an event has occurred which ispotentially damaging to a company's reputation, e.g., a news story abouta defective product, the conversations about the event in whichinfluential individuals are participating may be tracked for the purposeof devising an appropriate strategy for dealing with the crisis.

Media outlets (e.g., news organizations) can leverage the ecosystemarchitecture in a wide variety of ways. For example, the ecosystem maybe used by a news site to understand how people are responding to itsstories. That is, such outlets can incorporate event notification intotheir publishing systems so that each time an article is published, theyping the ecosystem to get indexed as described above. Then they can seewho is talking about and linking to those stories and what they aresaying.

Similarly, the operator of a news site can ask for the most popularstories published on its site in the past 12 hours, e.g., as indicatedby the number of links to those stories. This “buzz” about a story canalso be tracked over time, or compared to the buzz generated by a storyabout the same topic from a competitor's site. In addition, some measureof “scoop” protection may also be ensured in that the time of the ping(which corresponds to the original posting of a story) is stored in thedatabase.

To add another layer, not only can the news site track the buzz, some ofthe tracked information can be embedded in the original story on thenews site so that readers can see what others are saying about thestory, e.g., a real-time “letters to the editor.” More generally,representations of the near real time information available from thedatabase (e.g., as embodied in graphs and charts or even raw data) canbe presented live via a variety of media. For example, such informationfeeds could be provided in television programs in association withparticular topics or as real time feedback for television programs(e.g., news, variety, talk shows, talent search, etc.).

Media outlets can also mine the ecosystem database to identifyauthoritative individuals who might be useful as sources for newarticles, or might be attractive to recruit as new employees. Moregenerally, because the database indexes information by authority, asearch could be conducted for the most influential or authoritativepeople in any given subject matter area for any reason whatsoever.

It should be noted that database(s) 106 FIG. 1 may be configured in avariety of ways to suit particular implementations without departingfrom the scope of the invention. It will also be understood thatmaintaining one or more relational database in which large numbers ofinserts, updates and deletes are being performed simultaneously with alarge number of selects is a difficult problem, particularly as the sizeof the database increases.

Therefore, according to a specific embodiment of the invention, a methodis provided in which SQL databases are multiplexed to create a scalable,sharded, clustered database system 300 shown in FIG. 3. Individual SQLimplementations running on networked hardware are linked and thedatabase is fragmented onto individual clusters. Each fragment of thedatabase runs on a single shard of the entire database. Each databaseshard is made up of a cluster of machines, one acting as the read-writemaster 302, and the other machines acting as read-only slaves 204 whichcontain copies of the master. Read requests can be distributed among anarbitrarily large number of slaves 204. Each shard is indexed on asingle unique index, e.g., blog ID, and all information related to thatindex is stored on that shard. This approach allows all of the data tobe maintained in RAM, resulting in suitably fast response times.

A separate database (the sourcesdb 206) is used to keep information onwhat shard contains information relating to that specific index. Eachmultiplexer (mux 208) contains a local in-memory copy of the databasecontaining only the schemas and none of the data. This in-memory copy ofthe database is called the muxdb. Each mux connects to the databases oneach shard and multiplexes queries out to one or more shards afterparsing each incoming query and depending on the specific query(SELECT/INSERT/UPDATE/DELETE, etc) and whether the query is pivoting onthe sharded index. For queries pivoting on the sharded index, themultiplexer talks only to the shard containing the data for the index inquestion. For queries that are not pivoting directly on the shardedindex, the query is sent to all of the shards, and the responses arethen collected by the mux in parallel and then a final collation of thedata occurs when the a new table is created inside the muxdb using theoriginal query as a table definition, and then the results of theparallel sharded queries are inserted and the original query is run onthe new, much smaller, in-memory table.

The muxes can be parallelized as well, creating a large redundantsystem. In addition, if a query times out, the mux marks the shard wherethe query was sent so that the bad database inside of the cluster can beremoved or repaired. Lastly, new shards can be added to the system asthe size of the clustered index grows, and more slaves can be added toeach shard as the number of read queries to the overall system grows.This allows the delivery of real-time results even as load on theoverall system grows, and increased I/O throughput to the entire systemeven as the amount of data in the system grows.

According to one implementation, a computersdB is maintained whichmaintains a list of computers in the grid, their roles, shard IDs, andstatuses (online, offline, busy, repair, etc.). The muxes use thisinformation for failover and to dynamically grow/shrink the gridreliably.

While the invention has been particularly shown and described withreference to specific embodiments thereof, it will be understood bythose skilled in the art that changes in the form and details of thedisclosed embodiments may be made without departing from the spirit orscope of the invention. In addition, although various advantages,aspects, and objects of the present invention have been discussed hereinwith reference to various embodiments, it will be understood that thescope of the invention should not be limited by reference to suchadvantages, aspects, and objects. Rather, the scope of the inventionshould be determined with reference to the appended claims.

What is claimed is:
 1. A computer-implemented method of data aggregationin a network, comprising: receiving event notifications from a pluralityof content sites on the network, each event notification indicatingoccurrence of an event associated with a corresponding one of thecontent sites, each event corresponding to a posting of content on thecorresponding content site by an individual; in response to each eventnotification, generating event metadata, the event metadata including atime stamp for the event and change data corresponding to the posting ofcontent, the event metadata for selected ones of the events includeinbound link data representing links pointing to the content associatedwith the selected events; indexing the event metadata in anordered-by-authority database in which the event metadata correspondingto the selected events are ordered with reference to the inbound linkdata; and identifying authoritative ones of the individuals for each ofa plurality of categories with reference to the inbound link data in theordered-by-authority database representing inbound links pointing to thecontent posted by the authoritative individuals.
 2. The method of claim1 wherein the event notifications are generated by event notificationcode associated with content publishing code.
 3. The method of claim 2wherein the content publishing and event notification codes both resideon selected ones of the content sites.
 4. The method of claim 3 whereinthe event notification code is integrated with the content publishingcode on at least some of the selected content sites.
 5. The method ofclaim 2 wherein at least a portion of the content publishing and eventnotification codes resides on a third party service provider networkseparate from and associated with selected ones of the content sites. 6.The method of claim 2 wherein the content publishing code comprises anyof a web log publishing tool, a wiki web page editing tool, a socialnetwork profile editing tool, a content management system tool, and apersonal publishing tool.
 7. The method of claim 1 further comprising,in response to selected ones of the event notifications, retrieving atleast a portion of the event metadata from the corresponding contentsites, wherein retrieving at least a portion of the event metadatacomprises one or more of spidering the corresponding site, inferringknown metadata locations for feeds, or inferring known metadatalocations for profile pages.
 8. The method of claim 1 wherein the eventmetadata for each event further relates to any of a uniform resourcelocator (URL) associated with the content site corresponding to theevent, a permalink associated with the posting of content, a contentcreator identifier corresponding to the individual posting the content,an event type identifier, an event identifier, the content, at least onekeyword relating to the content, inbound links to the content, outboundlinks from the content, or any structured data or metadata associatedwith the event.
 9. The method of claim 1 further comprising indexing allof the event metadata in a global database.
 10. The method of claim 1further comprising indexing all of the event metadata in anordered-by-time database primarily with reference to the time stamp. 11.The method of claim 1 wherein the event metadata for particular ones ofthe events include keyword data relating to keywords identified in thecontent associated with the particular events, the method furthercomprising indexing the event metadata for the particular events in anordered-by-keyword database primarily with reference to the keyworddata.
 12. The method of claim 1 wherein identifying the authoritativeindividuals for each category comprises identifying specific content inthe category generated by the authoritative individuals with referenceto a number of inbound links associated with the specific content. 13.The method of claim 1 wherein identifying the authoritative individualsfor each category comprises identifying first specific content in thecategory directed to which second specific content associated with theauthoritative individuals includes outbound links.
 14. The method ofclaim 1 further comprising tracking responses of a plurality ofresponding individuals to a specific event, wherein tracking of theresponses is done with reference to responsive content generated by theresponding individuals and indexed in the plurality of databases. 15.The method of claim 1 wherein the indexing of the event metadata foreach event occurs within one of 12 hours, six hours, three hours, twohours, one hour, 10 minutes, or 2 minutes.
 16. A system for facilitatingdata aggregation in a network, the system comprising one or morecomputing devices, the one or more computing devices including memoryand one or more processors configured to: receive event notificationsfrom a plurality of content sites on the network, each eventnotification indicating occurrence of an event associated with acorresponding one of the content sites, each event corresponding to aposting of content on the corresponding content site by an individual;generate event metadata in response to each event notification, theevent metadata including a time stamp for the event and change datacorresponding to the posting of content, the event metadata for selectedones of the events include inbound link data representing links pointingto the content associated with the selected events; index the eventmetadata in an ordered-by-authority database in which the event metadatacorresponding to the selected events are ordered with reference to theinbound link data; and identify authoritative ones of the individualsfor each of a plurality of categories with reference to the inbound linkdata in the ordered-by-authority database representing inbound linkspointing to the content posted by the authoritative individuals.
 17. Thesystem of claim 16 wherein the one or more computing devices are furtherconfigured to, in response to selected ones of the event notifications,retrieve at least a portion of the event metadata from the correspondingcontent sites by one or more of spidering the corresponding site,inferring known metadata locations for feeds, or inferring knownmetadata locations for profile pages.
 18. The system of claim 16 whereinthe event metadata for each event further relates to any of a uniformresource locator (URL) associated with the content site corresponding tothe event, a permalink associated with the posting of content, a contentcreator identifier corresponding to the individual posting the content,an event type identifier, an event identifier, the content, at least onekeyword relating to the content, inbound links to the content, outboundlinks from the content, or any structured data or metadata associatedwith the event.
 19. The system of claim 16 wherein the one or morecomputing devices are further configured to index all of the eventmetadata in a global database.
 20. The system of claim 16 wherein theone or more computing devices are further configured to index all of theevent metadata in an ordered-by-time database primarily with referenceto the time stamp.
 21. The system of claim 16 wherein the event metadatafor particular ones of the events include keyword data relating tokeywords identified in the content associated with the particularevents, and wherein the one or more computing devices are furtherconfigured to index the event metadata for the particular events in anordered-by-keyword database primarily with reference to the keyworddata.
 22. The system of claim 16 wherein the one or more computingdevices are configured to identify the authoritative individuals foreach category by identifying specific content in the category generatedby the authoritative individuals with reference to a number of inboundlinks associated with the specific content.
 23. The system of claim 16wherein the one or more computing devices are configured to identifyingthe authoritative individuals for each category by identifying firstspecific content in the category directed to which second specificcontent associated with the authoritative individuals includes outboundlinks.
 24. The system of claim 16 wherein the one or more computingdevices are further configured to track responses of a plurality ofresponding individuals to a specific event, wherein tracking of theresponses is done with reference to responsive content generated by theresponding individuals.
 25. The system of claim 16 wherein the indexingof the event metadata for each event occurs within one of 12 hours, sixhours, three hours, two hours, one hour, 10 minutes, or 2 minutes. 26.The system of claim 16 wherein the one or more computing devices areconfigured to identify the authoritative individuals for each categoryby determining an authority level of each of the authoritativeindividuals with reference to a number of inbound links associated withthat authoritative individual.
 27. The system of claim 16 wherein theone or more computing devices are configured to identify theauthoritative individuals for each category by determining an authoritylevel of each of the authoritative individuals with reference to one ormore other authority levels for other authoritative individualscorresponding to the inbound links associated with that authoritativeindividual.
 28. The system of claim 16 wherein the one or more computingdevices are configured to identify the authoritative individuals foreach category by determining an authority level of each of theauthoritative individuals with reference to one or more of thecategories associated with other authoritative individuals correspondingto the inbound links associated with that authoritative individual. 29.The system of claim 16 wherein the one or more computing devices areconfigured to index the event metadata in the ordered-by-authoritydatabase by indexing the event metadata across a plurality of databasesegments having different sizes, the event metadata for first ones ofthe authoritative individuals having high authority levels being indexedin smaller ones of the database segments than the event metadata forsecond ones of the authoritative individuals having low authoritylevels.
 30. The system of claim 16 wherein the one or more computingdevices are further configured to identify one or more recent contentpostings for one or more of the authoritative individuals for a specificone of the plurality of categories.
 31. The system of claim 16 whereinthe one or more computing devices are further configured to determine asearch engine relevancy score for a content posting with reference toone or more authority values associated with a corresponding one of theauthoritative individuals.
 32. The system of claim 16 wherein the one ormore computing devices are further configured to identify one or more ofthe authoritative individuals that posted content relating to aparticular topic that became a focus of a subsequent news event.
 33. Thesystem of claim 16 wherein the one or more computing devices are furtherconfigured to identify currently relevant content postings withreference to the inbound link data.
 34. The system of claim 33 whereinthe one or more computing devices are further configured to identify oneor more of the categories for selected ones of the currently relevantcontent postings.
 35. The method of claim 1 wherein identifying theauthoritative individuals for each category comprises determining anauthority level of each of the authoritative individuals with referenceto a number of inbound links associated with that authoritativeindividual.
 36. The method of claim 1 wherein identifying theauthoritative individuals for each category comprises determining anauthority level of each of the authoritative individuals with referenceto one or more other authority levels for other authoritativeindividuals corresponding to the inbound links associated with thatauthoritative individual.
 37. The method of claim 1 wherein identifyingthe authoritative individuals for each category comprises determining anauthority level of each of the authoritative individuals with referenceto one or more of the categories associated with other authoritativeindividuals corresponding to the inbound links associated with thatauthoritative individual.
 38. The method of claim 1 wherein indexing theevent metadata in the ordered-by-authority database comprises indexingthe event metadata across a plurality of database segments havingdifferent sizes, the event metadata for first ones of the authoritativeindividuals having high authority levels being indexed in smaller onesof the database segments than the event metadata for second ones of theauthoritative individuals having low authority levels.
 39. The method ofclaim 1 further comprising identifying one or more recent contentpostings for one or more of the authoritative individuals for a specificone of the plurality of categories.
 40. The method of claim 1 furthercomprising determining a search engine relevancy score for a contentposting with reference to one or more authority values associated with acorresponding one of the authoritative individuals.
 41. The method ofclaim 1 further comprising identifying one or more of the authoritativeindividuals that posted content relating to a particular topic thatbecame a focus of a subsequent news event.
 42. The method of claim 1further comprising identifying currently relevant content postings withreference to the inbound link data.
 43. The method of claim 42 furthercomprising identifying one or more of the categories for selected onesof the currently relevant content postings.